Sourced from dogstatsd-ruby's changelog.

5.3.2 / 2021.11.03

• [OTHER] add a warning message for the v5.x update on install #222 by @​djmitche

5.3.1 / 2021.10.21

• [OTHER] restore connection opening behavior from before 5.3.0 (connections not opened on client instantiation but on the first write instead) #214][] by [@​remeh][]

5.3.0 / 2021.10.06

• [ENHANCEMENT] Automatically re-allocate resources (e.g. background thread) if dogstatsd-ruby is used in an application using forks #205[] by [@​remeh][]

  This will help in scenarios where applications are not handling cleanup/re-creation of the dogstatsd-ruby instances in forked processes. If you are an user of v4.x versions of dogstatsd-ruby and want to migrate to v5.x, please make sure to go through this section of the README and through the migration guide.

• [BUGFIX] Fix client telemetry in applications using forks #205[] by [@​remeh][]

Please note that this version will emit a deprecation message if you are using ruby < 2.1: we plan to drop support for ruby 2.0 in a future minor release.

5.2.0 / 2021.07.01

• [FEATURE] Add single_thread mode for users having issues with the companion thread. #194[] by [@​remeh][]

You can use this mode to avoid spawning a companion thread while using v5.x versions:

# Import the library
require 'datadog/statsd'
Create a DogStatsD client instance.
statsd = Datadog::Statsd.new('localhost', 8125, single_thread: true)
...
release resources used by the client instance and flush last metrics
statsd.close()

Note that if you want to restore the behavior of v4.x versions, you can also configure the buffer to flush on every metric submission:

# Import the library
require 'datadog/statsd'
Create a DogStatsD client instance using UDP
statsd = Datadog::Statsd.new('localhost', 8125, single_thread: true, buffer_max_pool_size: 1)

5.1.0 / 2021.06.17

• [FEATURE] Flush last metrics on Statsd#close #180[] by [@​kbogtob][]
• [ENHANCEMENT] Do not try to flush where there is no available message_queue #189[] by [@​remeh][]
• [OTHER] Add pry to development dependencies and enable gem in Gemfile #192[] by [@​ivoanjo][]

... (truncated)

• d833672 Merge pull request #223 from DataDog/release-5.3.2
• 54f1054 prep for 5.3.2 release
• b37e15a Merge pull request #222 from DataDog/issue221
• 01a77df add a post_install_message about the v5 update
• caf46e3 Merge pull request #220 from DataDog/dustin.mitchell/ac-1046
• 23d1cef Merge pull request #218 from DataDog/add-stale-bot
• 654e32d add spec test for event unicode encoding
• d6b4c3e Merge pull request #217 from DataDog/add-codeowners
• b699728 configure probot-stale
• e0fcb2d add CODEOWNERS sending reviews to maintainers
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)